???

Thank you for your reply. We do not have separate index data for files in the documentDirectory path. Since we use the FileManager API to retrieve and display the list in real time, we can display it as an update if the path has changed. We also update the documentDirectory path every time before retrieving the file list. There were no inquiries about this issue until iOS 17, but there were several similar inquiries in iOS 18.

We continued to test the app debugging or even the app distributed as a test flight, but the same symptom did not reproduce. There is no specific work in the app's code to stop music playback or do anything when switching from "foreground" to "background" state.

The OS applies to both iOS and iPadOS. The app background mode is checked in the "Audio, Airplay, and Picture in Picture" section. It is judged that the music being played stops in all cases of "Move to Home Screen" and "Switch to another app" while playing a music file. Originally, the playback should continue in all of the above cases.

It looks like this issue has not been resolved in 17.5.1 yet. I sent feedback on several iOS bugs and error issues other than this issue, but some have not been resolved for several years and some have not been resolved for several months. So, there was no feedback on this issue either.

This is different from the issue I gave feedback on. Even before that issue, this happened occasionally.

Oh, there is someone experiencing a similar issue. We tested it and found that it was not a watch problem. There were no issues with Watch 10.4 or 10.5. There has been this issue since iPhone 17.5 when transferring files.

By the way, have you ever been rejected or encountered any problems during app review?

Are you saying that the user should be able to turn the isExcludedFromBackup option on/off? Thank you for answer.

Thank you for answer. The router is in another room, so I'm going to purchase a new router and place it in the same room as my MacBook, iPhone, and Apple Watch.

It's still happening in iOS 16. Not even fixed in iOS 16

Also in your code, if the autorelasepool error occurs after the stop call, it crashes at the "synthesizer = nil" location and the app dies.

Currently, when AVSpeechSynthesizer stop is continuously performed on iOS 16 or later devices, the AVSpeechSynthesizer object is released, resulting in an error or loss of voice control and reading to the end of the current sentence. So I was wondering if there is any other way other than using the function of AVSpeechSynthesizer .

Both stopSpeaking(at: .word) or stopSpeaking(at: .immediate) won't stop after stopping the AVSpeechSynthesizer if an error occurs and the voice playback control is lost. Also use word or immediate to stop the current playback before the AVSpeechSynthesizer error.

We are currently uploading this issue through the Feedback app (installed on beta iOS versions). Feedback ID is FB11711356. We are waiting because this issue affects the apps we sell. Could you please let me know if this issue or feedback is ongoing or what is going on? If the iOS issue is correct and can be improved, we will try to answer that users will improve it with an iOS update when they inquire about the problem.